Over a year ago I spent several weeks researching, talking to Tom and a couple of knowledgeable KFLOP users and quickly got lost in the weeds. That coupled with the install error at the time and many many other things going on, the project sat there. You know how it goes.

Hi Michael,

Although possible to save parameters to KFLOP we don't recommend it.  We recommend to always leave KFLOP in a virgin state and let it be initialized by your KMotion.exe Screen settings or by your initialization C Program.  If you did flash parameter settings into a KFLOP they wouldn't necessarily appear in the KMotion.exe screens unless you upload the settings from KFLOP into the screens.

Settings in KMotion.exe screens persist from one run to the next because they are saved in a file \KMotion\Data\config.txt

KMotion.exe Screen Axis settings can also be loaded/saved as *.mot files.

KMotion.exe Screen Axis settings can also be imported from an initialization C Program that you have previously created.

This Flash video may help you understand:
http://dynomotion.com/Help/FlashHelp/Parameters/index.html

Its up to you to keep track of what you have changed and what files you have created and where you have saved them.

It might be better for you to start from scratch so you know what you have done.  Its not that hard once you know what you are doing.

HTH
Regards
TK

 

Over a year ago I spent several weeks researching, talking to Tom and a couple of knowledgeable KFLOP users and quickly got lost in the weeds. That coupled with the install error at the time and many many other things going on, the project sat there. You know how it goes.

Anyway, the good news is I'm getting back up to speed. Thankfully I took great notes. The encoder Morray linked to is inexpensive and looks serviceable so I ordered one to try. I'll have to figure out how to rig it but even worse case I could use a friction wheel running against the main timing belt - at least temporarily to get things configured. Meanwhile, it's back to configuring the KFLOP/KSTEP and finishing off the control box to hold the power supply, eStop circuitry and KFLOP/KSTEP.

I moved the PC I'm using to control the lathe to my office so I can relax while working on this. I updated to Windows 10 (from 7) and I'm really pleased with the performance and usability. I'd already updated 4 other PCs so knew what to expect. 

Before I update I want to make sure I recover what I had previously done. So I launched KMOTION and have some questions.

I did not have the KFLOP/KSTEP hooked up via USB when I launched KMOTION. I do not see any of the configuration that I had previously done. There is no File->Load parameters so I'm guessing everything resides on KFLOP and if I connected it I would see what was loaded? Is there a way to save this type of config? I did find my C program - which I called user1 for some reason - and am able to load and compile it.

Before I upgrade KMOTION and the firmware I want to make sure I won't lose any past work - but first I need to make sure I defamiliarize myself with the past work.

Any recommendations? Can I upgrade without fear of losing my previous work? I am going to zip and save the entire dynomotion folder as a backup, I just want to know what to expect.

Michael

  

Thanks Tom. That's the fact of the matter "it's not that hard once you know what you are doing!" It's getting to know what you are doing that's the painful part!

Thanks Tom, the flash video was helpful. I remember watching that before.

And the pain picks up where I left off unfortunately.

Yes, I get a version string that is correct.

Here's the code:

Ok, so I started with the 3 axis KSTEP sample, removed channel 2 (keeping 0 and 1), reorganized the axes for the lathe (Z = channel 0, X = channel 1), etc. I added the same printf line at the top of the main(), compiled, uploaded and ran. Still no message printed. Version returns the correct firmware version, ClearBit:47 turns off the correct LED on the board.  Thread 1 is selected in the program window. 

One last try. I copied and pasted the simple Hello World from the wiki and get nada. Even power cycling does not print Hello World. Version from the console gives the version info, the KFLOP is connected. No compile errors. Can't tell if the program downloads as per my previous post.

Hi Michael,

Power cycling won't execute programs unless they have been Flashed into KFLOP Memory and Configured to "Launch on Power up".

Strange you are having so much trouble with all the basics.  I can't think of why something so simple wouldn't work unless you are doing something strange like mixing versions, or have flashed programs to KFLOP, or have multiple Versions running.

So I would suggest first making sure KFLOP is restored to defaults with:

#1 Turn off KFLOP Power
#2 Reboot PC
#3 Run \KMotion433\Release\KMotion.exe
#4 Turn on KFLOP
#5 Use Config\Flash Screen to Flash "New Version"
#6 Exit KMotion.exe
#7 Turn off KFLOP Power

Now test executing a program to print to Console

#1 Run \KMotion433\Release\KMotion.exe
#2 Turn On KFLOP
#3 Open Console Screen
#4 Enter "Version" Verify Firmware Version is V4.33
#5 Open C Programs Screen
#6 Select Thread #1
#7 Open file "print.c"
#8 Push Save/Compile/Download/Run (button with 6 arrows)
#9 Check if "Hello World" is printed on the Console Screen

HTH
Regards
TK

 

One last try. I copied and pasted the simple Hello World from the wiki and get nada. Even power cycling does not print Hello World. Version from the console gives the version info, the KFLOP is connected. No compile errors. Can't tell if the program downloads as per my previous post.

Thanks Tom. I understand about flashing and had actually also tested by power cycling after flashing. I think I'm just cursed, maybe I upset the M*** gods when they caught wind I'm using KFLOP?

Attachments :

Screen Shot 2016-04-06 at 1.49.03 PM-13092.png

Next up...

Thanks Moray, I understand that about the source you see is not running until you explicitly upload it and run it. I have not even launched KMotionCNC yet! 

I've decided to hook up a small test bed in my office (like in Tom's video) while I complete assembly of my control box. Basically, this consists of 2 small NEMA 17 steppers (<1A) and a 12V DC power supply. My goal is to hook these up and get them to run lathe gcode. I want to sanity check everything so I don't release the magic smoke. I've annotated my questions in bold.

Hi Michael,

That all sounds correct.  Although when you use the word "power" you might be specific about what power you are referring to.

Install KFLOP USB jumper J3 and KSTEP Isolation jumpers JP34 and JP35 to supply both KFLOP and KSTEP +5V from USB. 

Yes you can use either GND or VB terminals on KSTEP J1.  If your total current is more than 10Amps use both connections.  It is not in your case.

HTH
Regards
TK

 

I've decided to hook up a small test bed in my office (like in Tom's video) while I complete assembly of my control box. Basically, this consists of 2 small NEMA 17 steppers (<1A) and a 12V DC power supply. My goal is to hook these up and get them to run lathe gcode. I want to sanity check everything so I don't release the magic smoke. I've annotated my questions in bold.

I started with Tom's video: https://www.youtube.com/watch?v=pW-9fDLAn2s and http://www.dynomotion.com/Help/SchematicsKStep/ConnectorsKStep.htm to hook up KFLOP and KSTEP.

Since my steppers are <1A I do not need any current setting jumpers.

I have all 3 jumpers on the voltage clamp pins ABC.

I am using steppers that I use on my 3D printers and have verified the coils. These are hooked up to J2 (motor 0 which will be my Z axis) and J3 (motor 1 which will be my X axis).

Currently I have the jumper on J3 on the KFLOP so I could test with USB power - this was before setting this test bed up. First question, since I am going to provide power through the KSTEP J1, I need to leave that jumper in place and power the board from USB, correct? The 12VDC supply will be connected to J1 on the KSTEP. I assume that I can use either GND and either VB terminal on the four terminal, is that correct? (why are there 2 sets of terminals on J1?)

The isolation jumpers are installed on JP34 and JP35 since I'm powering the board from USB.

I think that's everything. I'll wait for verification that this is correct before powering up as my luck to date has been on the "bad" side!

Attachments :

Screen Shot 2016-04-07 at 10.46.12 AM-13107.png

This is much like that old Three Stooges episode...

G20

F12

G0 X0 Z0

G18

G2 Y0 Z0 I0 K1.0

M2

and I'm getting what looks to be correct coordinated motion and the G Code Viewer is showing a circle in the XZ axis view. Things are looking good with the basic 2 axis control. 

I haven't spent time with KMotionCNC in the past so now I need to get up to speed with that over the next few days while I work on my control box. Is it configurable to create a basic lathe screen or does that require VisualStudio programming?

 

 

Ok, found the screen "faces" drop down in tool setup. I'll go quiet now and read help and the wiki before asking pesky questions!

Ok, I'm back! I spent a bit of time reading a lot of docs and experimenting but I have a persistnant issue I don't understand and can't seem to change. The issue is that in KMotionCNC the X axis DRO updates when I jog the with the Z jog buttons and vice versa. So I stepped back and reconfigured things like this:

It turns out that there is a checkbox on the Tool Setup->Trajectory Planner tab in the Lathe Options box called Lathe. Check that and all is well. A google search found it: http://www.dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm

Hi Michael,

#1 Estop is a complex subject with many possibilities.  Please research the forums

#2 See the SimpleHomeIndexFunctionTest.c example

#3 assign associated I/O bit to M Codes

#4 See  Analog Output Section here:
http://dynomotion.com/Help/SchematicsKStep/UsingKStep.htm

See the example: \C Programs\KStep\KMotionCNC\Spindle_S_Kstep.c

HTH
Regards
TK

 

It turns out that there is a checkbox on the Tool Setup->Trajectory Planner tab in the Lathe Options box called Lathe. Check that and all is well. A google search found it: http://www.dynomotion.com/Help/KMotionCNC/ToolSetupScreenTP.htm

Now I'm off to the races. I'm working on my eStop routine and have a basic estop handler implemented (simple). The questions I have now are around best practices with KSTEP and KFLOP for doing things like:

1) estop handling

2) HOME handling

2) using the KSTEP relays drivers (for coolant, etc)

3) using the KSTEP analog out for VFD spindle control 

Are there any published real world examples of these?

I've looked through the sample code and that has been helpful. I assume that the simple samples that demonstrate something in a while{} in a simple main can just be taken and put into my program's while{} or is the intent that these are run in individual threads?

Thanks Moray. Actually, I guess I didn't ask my question clearly enough! I've built 5 CNC machines (mills and a router) and 8 3D printers. The mills at least all have good eStop handling, etc. What I meant to ask was what are some best programming practices in KMotion for these tasks? My machines are not huge production floor machines. The lathe I'm working on is a Grizzly G0602 conversion (a 10" x 22" lathe).